Any hope to see that PR merged?

Please merge this!

allow user to custom file permission , use default if not configured。 I think this is better for users @natefinch

Yes the current behavior is not great.

I think using the same permission (0755) as the parent folder could also be feasible.

When working with sidecar to collect logs in Kubernetes, this issue becomes quite visible. @jedisct1

I think using the same permission (0755) as the parent folder could also be feasible.

0644 would be more appropriate for files, we don't need to be able to execute log files.

I think using the same permission (0755) as the parent folder could also be feasible.

0644 would be more appropriate for files, we don't need to be able to execute log files.

Yes, changing the file permission to 0644 is sufficient and there is no need to customize the permission further.

#186

I think using the same permission (0755) as the parent folder could also be feasible.

0644 would be more appropriate for files, we don't need to be able to execute log files.

Yes, changing the file permission to 0644 is sufficient and there is no need to customize the permission further.

#186

I would disagree, having the ability to have restrictive or open permissions on log files is very important in a security sense.
I would prefer this PR over yours.

I think using the same permission (0755) as the parent folder could also be feasible.

0644 would be more appropriate for files, we don't need to be able to execute log files.

Yes, changing the file permission to 0644 is sufficient and there is no need to customize the permission further.
#186

I would disagree, having the ability to have restrictive or open permissions on log files is very important in a security sense. I would prefer this PR over yours.

Strict file permissions meet security requirements. Hope to be merged.

Is there any hope for this to be merged? Or even reviewed by the owners. So that it could eventually be merged.

+1

I would also like this merged. I think that a library forcing permissions should be a "last resort" option. I totally understand why gpg and ssh do it, but it makes little to no sense for logs. The authors of this library don't have context for which the logs are being used. Having a strict default is fine as long as it is configurable (as it is with this PR).

please merge this!

@natefinch please merge this